← previous blocknext block →recent activity
Analyzing
Block #76,115,267
12 transactions · 10 stateful · 2026-05-21 20:18:07 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,115,267 · 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
1w02w13w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x9337b1cc…49c0
0x065c9d…c394
3 touches
1 conflict
0xa4315739…9709
0x065c9d…c394
3 touches
1 conflict
0x7c548480…b329
0x5487db…7777
2 touches
1 conflict
0x28dde4ce…6ae3
0x065c9d…c394
2 touches
0 conflicts
0x2dcd5a22…c654
0x065c9d…c394
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
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 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity