← previous blocknext block →recent activity
Analyzing
Block #75,688,172
6 transactions · 6 stateful · 2026-05-19 20:52:18 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,688,172 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6170b3c…fc27
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x3d652580…34e7
0x065c9d…c394
3 touches
1 conflict
0x5f7f57ef…499b
0x065c9d…c394
3 touches
1 conflict
0x30811730…ea5a
0x065c9d…c394
2 touches
0 conflicts
0x3d0860dd…ef3f
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x687de3d8…4fd6
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 0xe6170b3cb8…16fc27
Audit this contract →
← previous block·next block →recent activity