← previous blocknext block →recent activity
Analyzing
Block #76,387,354
11 transactions · 9 stateful · 2026-05-23 02:30:23 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,387,354 · 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
1w02w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbae68db8…86e3
0x065c9d…c394
4 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
4 touches
1 conflict
0xd5bfc8fb…071f
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5d729eb5…827c
0xa6afd3…d132
3 touches
1 conflict
0xa0aafbc4…701f
0x0594c7…a3be
2 touches
0 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
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 0xbae68db89d…a186e3
Audit this contract →
← previous block·next block →recent activity