← previous blocknext block →recent activity
Analyzing
Block #73,663,814
7 transactions · 6 stateful · 2026-05-10 11:24:15 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,663,814 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x0175b7a6…1dbd
0x6c4bfa…a540
4 touches
1 conflict
0x0c89ea7e…13eb
0x6c4bfa…a540
4 touches
1 conflict
0x0ef1e663…8f2a
0x6c4bfa…a540
4 touches
1 conflict
0x2e2214a9…fe0d
0x6c4bfa…a540
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6c4bfa…a540
4 touches
1 conflict
0x5b3dfef8…a676
0x6c4bfa…a540
4 touches
1 conflict
0xaa03918c…f1c7
0x6c4bfa…a540
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: 0xc8689a47…62ee79
1 conflict on slot 0xed57bddf8e…bd1abf
Audit this contract →
← previous block·next block →recent activity