← previous blocknext block →recent activity
Analyzing
Block #76,482,474
10 transactions · 9 stateful · 2026-05-23 13:03:14 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,482,474 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
6 touches
3 conflicts
0x06e40499…165e
0x1d1325…2305
6 touches
3 conflicts
0xa17ec269…7cdd
0x1d1325…2305
6 touches
3 conflicts
0xa605468c…1bfc
0x1d1325…2305
6 touches
3 conflicts
0xc8525006…2b45
0x1d1325…2305
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity