← previous blocknext block →recent activity
Analyzing
Block #75,014,264
6 transactions · 5 stateful · 2026-05-16 17:43:55 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,014,264 · 6 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
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xaa12290e…a193
0x065c9d…c394
4 touches
1 conflict
0x24477417…27e0
0x065c9d…c394
2 touches
0 conflicts
0x5519f26e…eed7
0x065c9d…c394
2 touches
0 conflicts
0x5d0a88e3…77e0
0x065c9d…c394
2 touches
0 conflicts
0x6f82f72d…0e7e
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 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity