← previous blocknext block →recent activity
Analyzing
Block #94,862,086
19 transactions · 18 stateful · 2026-08-10 19:45:20 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,862,086 · 19 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
2w03w04w16w07w18w210w312w413w517w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76736068…b82d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x94de4d05…ad01
0x34b655…2a6f
8 touches
6 conflicts
0x673e2e56…9f5d
0x34b655…2a6f
6 touches
3 conflicts
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x75c6640e…5be8
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
15 conflicts on slot 0x7673606805…f3b82d
Audit this contract →
← previous block·next block →recent activity