← previous blocknext block →recent activity
Analyzing
Block #75,890,381
12 transactions · 9 stateful · 2026-05-20 19:20:06 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,890,381 · 12 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
1w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x1af02b04…5c21
0x065c9d…c394
2 touches
0 conflicts
0x217d3916…708a
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x9ba4a9aa…7ede
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity