← previous blocknext block →recent activity

Analyzing

Block #73,982,009

12 transactions · 10 stateful · 2026-05-11 22:56:14 UTC

Parallelism

58/100

Blocked

40%

Avg conflicts / tx

1.17

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,982,009  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x0621aa11…ae88

0x065c9d…c394

4 touches
1 conflict

0xc30ab48a…8370

0x065c9d…c394

3 touches
1 conflict

0x4a2a8c4d…7799

0x065c9d…c394

3 touches
1 conflict

0x639a0848…50a3

0x065c9d…c394

3 touches
1 conflict

0x16095494…5665

0x065c9d…c394

3 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x2a68ba18…8e90c5

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity