← previous blocknext block →recent activity
Analyzing
Block #94,851,182
15 transactions · 15 stateful · 2026-08-10 18:50:30 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,851,182 · 15 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
1w02w13w24w05w18w29w311w413w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51611059…097e
0x34b655…2a6f
8 touches
6 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb0608dfe…083d
0x34b655…2a6f
4 touches
1 conflict
0xd60f3925…0800
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x1b8f048a…581d
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x516110595e…7a097e
Audit this contract →
← previous block·next block →recent activity