← previous blocknext block →recent activity
Analyzing
Block #73,967,615
15 transactions · 12 stateful · 2026-05-11 21:19:39 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,967,615 · 15 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
2w04w18w29w310w412w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x279398a3…350d
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x2c058970…7421
0x065c9d…c394
4 touches
1 conflict
0xd1abda48…767e
0x065c9d…c394
4 touches
1 conflict
0x83d17b1a…4f52
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity