← previous blocknext block →recent activity
Analyzing
Block #94,225,626
20 transactions · 20 stateful · 2026-08-08 14:10:52 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,225,626 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w39w013w414w015w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfaa66cb5…f4c9
0x065c9d…c394
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x328ac514…9966
0xd32edf…ff58
3 touches
1 conflict
0x3a2355fc…ab3d
0x065c9d…c394
3 touches
1 conflict
0x997ccc40…4dfd
0x3bd359…433a
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
6 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity