← previous blocknext block →recent activity
Analyzing
Block #94,870,360
21 transactions · 19 stateful · 2026-08-10 20:26:57 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,870,360 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w28w010w112w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
8 touches
6 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
8 touches
6 conflicts
0x46b225ff…9d21
0x34b655…2a6f
8 touches
6 conflicts
0x3e04662b…0da5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…00c9
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
10 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity