← previous blocknext block →recent activity
Analyzing
Block #95,086,110
17 transactions · 16 stateful · 2026-08-11 14:32:56 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,086,110 · 17 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
1w02w13w24w27w38w412w513w314w616w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32626666…080c
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
8 touches
6 conflicts
0xa075e94f…e790
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x48203298…65cb
0x34b655…2a6f
6 touches
3 conflicts
0xb39cb1d8…effa
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 0x3262666637…ed080c
Audit this contract →
← previous block·next block →recent activity