← previous blocknext block →recent activity
Analyzing
Block #76,397,672
14 transactions · 9 stateful · 2026-05-23 03:38:55 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,397,672 · 14 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
1w02w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x263606ab…5a4b
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x62e31de8…3094
0xa6afd3…d132
4 touches
1 conflict
0x3d981301…e06f
0xd32edf…ff58
3 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
2 touches
0 conflicts
0x8720bc5e…cf09
0x754704…b603
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 0x263606ab53…c75a4b
Audit this contract →
← previous block·next block →recent activity