← previous blocknext block →recent activity
Analyzing
Block #76,339,821
9 transactions · 6 stateful · 2026-05-22 21:13:11 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,339,821 · 9 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
0x8805298e…ddee
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x94bfbf44…977b
0x065c9d…c394
3 touches
1 conflict
0x771dac61…2879
0x065c9d…c394
3 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x6688dd1c…1635
0x065c9d…c394
2 touches
0 conflicts
0x8339cabd…07a0
0x065c9d…c394
2 touches
0 conflicts
0xdda8fcf3…f411
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 0x8805298ea7…96ddee
Audit this contract →
← previous block·next block →recent activity