← previous blocknext block →recent activity
Analyzing
Block #74,666,735
7 transactions · 7 stateful · 2026-05-15 03:02:31 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,666,735 · 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9c3cc4d…b28d
0x065c9d…c394
4 touches
1 conflict
0xf5061a6a…ccf6
0x065c9d…c394
4 touches
1 conflict
0xbfe60fee…c2d9
0x065c9d…c394
3 touches
1 conflict
0x322d3529…d8f2
0x065c9d…c394
3 touches
1 conflict
0xf6701711…ee76
0x065c9d…c394
3 touches
1 conflict
0x46147e7c…f4d6
0x065c9d…c394
3 touches
1 conflict
0xdb178ecd…daca
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xe9c3cc4dbf…e9b28d
Audit this contract →
← previous block·next block →recent activity