← previous blocknext block →recent activity
Analyzing
Block #94,869,110
13 transactions · 12 stateful · 2026-08-10 20:20:40 UTC
Parallelism
39/100
Blocked
58%
Avg conflicts / tx
2.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,869,110 · 13 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
1w02w13w24w35w47w58w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3e4969…39e9
0x34b655…2a6f
14 touches
21 conflicts
0x9d615dde…2d97
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xa8488658…af8b
0x34b655…2a6f
8 touches
6 conflicts
0x95cad179…9b3d
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xac3e4969cf…1739e9
Audit this contract →
← previous block·next block →recent activity