← previous blocknext block →recent activity
Analyzing
Block #94,684,196
15 transactions · 15 stateful · 2026-08-10 04:49:02 UTC
Parallelism
33/100
Blocked
60%
Avg conflicts / tx
3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #94,684,196 · 15 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xe2e52e46…0894
0x34b655…2a6f
12 touches
15 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xcc1474f5…41f1
0x34b655…2a6f
8 touches
6 conflicts
0x21ef0807…d889
0x34b655…2a6f
8 touches
6 conflicts
0xdd6cf50f…e383
0x34b655…2a6f
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: Perpl
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity