← previous blocknext block →recent activity
Analyzing
Block #76,482,711
14 transactions · 11 stateful · 2026-05-23 13:04:48 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,482,711 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x587c9b6c…5aa8
0x065c9d…c394
3 touches
1 conflict
0x1916d5f9…f1b8
0x065c9d…c394
2 touches
0 conflicts
0x30c872fb…c7d6
0x065c9d…c394
2 touches
0 conflicts
0xcbaa1c55…2f07
0x065c9d…c394
2 touches
0 conflicts
0xf1ae2014…dea7
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity