← previous blocknext block →recent activity
Analyzing
Block #76,452,213
8 transactions · 7 stateful · 2026-05-23 09:41:40 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,452,213 · 8 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4a322a1…ac10
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xd3206e83…001a
0x065c9d…c394
3 touches
1 conflict
0x02525720…4ba0
0x065c9d…c394
3 touches
1 conflict
0x1d95f528…14b2
0x065c9d…c394
3 touches
1 conflict
0x74581e81…6b3e
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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 0xe4a322a163…cdac10
Audit this contract →
← previous block·next block →recent activity