← previous blocknext block →recent activity

Analyzing

Block #73,381,926

11 transactions · 9 stateful · 2026-05-09 04:05:33 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,381,926  ·  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

0xc4864452…fc40

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xf6fcd54d…f93a

0x065c9d…c394

3 touches
1 conflict

0x12606a5a…1f33

0x065c9d…c394

3 touches
1 conflict

0xa58891b7…ba4a

0x065c9d…c394

3 touches
1 conflict

0xe038916c…b1be

0x2a68ba…90c5

2 touches
0 conflicts

0x1a4b4152…0a08

0x8e764f…e322

2 touches
0 conflicts

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: 0x065c9d28…a9c394

1 conflict on slot 0xc486445227…8afc40

← previous block·next block →recent activity