← previous blocknext block →recent activity
Analyzing
Block #75,201,615
11 transactions · 9 stateful · 2026-05-17 14:34:09 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,201,615 · 11 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbe4e9c7…719a
0x065c9d…c394
4 touches
1 conflict
0xbcc461f3…b083
0x065c9d…c394
4 touches
1 conflict
0x9367710f…0d7e
0x065c9d…c394
4 touches
1 conflict
0xacbc2e41…4c47
0x065c9d…c394
3 touches
1 conflict
0x9b23e1dc…2477
0x065c9d…c394
3 touches
1 conflict
0x1e7973fc…bbbd
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0xa98c83a6…a65b
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 0xbbe4e9c74a…d5719a
Audit this contract →
← previous block·next block →recent activity