← previous blocknext block →recent activity
Analyzing
Block #94,840,711
17 transactions · 15 stateful · 2026-08-10 17:57:48 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,840,711 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w39w411w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbb0145cf…5450
0x34b655…2a6f
14 touches
21 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
8 touches
6 conflicts
0x5ca14c4d…33fb
0x34b655…2a6f
6 touches
3 conflicts
0x60a536a6…ef7a
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity