← previous blocknext block →recent activity
Analyzing
Block #94,796,234
17 transactions · 14 stateful · 2026-08-10 14:14:03 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,796,234 · 17 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
2w03w07w08w09w110w111w212w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x4e50038e…6e29
0x34b655…2a6f
4 touches
1 conflict
0xf6818217…345a
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xf362e8a6…6ce6
0x851145…3f07
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity