← previous blocknext block →recent activity
Analyzing
Block #76,723,581
11 transactions · 9 stateful · 2026-05-24 15:48:10 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,723,581 · 11 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb9fa4e6…e2cd
0x065c9d…c394
4 touches
1 conflict
0x44088124…d9b6
0x065c9d…c394
3 touches
1 conflict
0x62250553…cdb3
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ed5cfd0…d86e
0x065c9d…c394
2 touches
0 conflicts
0x4f4956f9…e86b
0x065c9d…c394
2 touches
0 conflicts
0x6fa42d99…834c
0x065c9d…c394
2 touches
0 conflicts
0x94e44376…cb98
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 0xdb9fa4e69c…59e2cd
Audit this contract →
← previous block·next block →recent activity