pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,746,548
← previous block
next block →
recent activity
Analyzing
Block #95,746,548
11 transactions · 10 stateful · 2026-08-13 22:09:28 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,746,548
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
0xab083028
#3
updatePrices
#4
0x5acec890
#5
0xcffefd2e
· blocks 2
#8
0xed82b078
#9
0x6a7e4110
#10
setData
#6
0xcffefd2e
#7
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xd93bcc30…6790
0x34b655…2a6f
4 touches
1 conflict
0xdba3b90b…02bd
0x34b655…2a6f
4 touches
1 conflict
0xdf00e2d7…5ada
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot
0xf18c12c49b…993e7d
Audit this contract →
← previous block
·
next block →
recent activity