← previous blocknext block →recent activity

Analyzing

Block #73,641,411

11 transactions · 7 stateful · 2026-05-10 08:53:17 UTC

Parallelism

73/100

Blocked

43%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,641,411  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x92799c73…56d0

0xd32edf…ff58

5 touches
3 conflicts

0xd32d3351…49ab

0xee8c0e…1242

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x4aae89e8…3e82

0x2a68ba…90c5

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0xba3d2100…4266

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x77503d6f…0781

0xa6afd3…d132

4 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: 0xd32edf66…9fff58

3 conflicts on slot 0x92799c7396…d856d0

← previous block·next block →recent activity