← previous blocknext block →recent activity
Analyzing
Block #75,032,447
9 transactions · 8 stateful · 2026-05-16 19:45:09 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,032,447 · 9 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
0x9d64bbfd…5fc9
0x065c9d…c394
4 touches
1 conflict
0xa86d63c7…8102
0x065c9d…c394
4 touches
1 conflict
0x667b0f14…cb3d
0x065c9d…c394
3 touches
1 conflict
0x1ecf8387…f90b
0x065c9d…c394
3 touches
1 conflict
0xf46d6040…c4b9
0x065c9d…c394
3 touches
1 conflict
0xfd697a8d…f360
0x065c9d…c394
3 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0xc9d81829…8266
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 0x9d64bbfd7f…b85fc9
Audit this contract →
← previous block·next block →recent activity