pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,707,894
← previous block
next block →
recent activity
Analyzing
Block #95,707,894
12 transactions · 10 stateful · 2026-08-13 18:54:45 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,707,894
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
0x39435dac
#4
0x39435dac
#5
updateDataFeedsValuesPartial
#6
0xcffefd2e
#7
forward
#8
0xcffefd2e
#9
setData
#11
0x61d59c2d
#2
0x5acec890
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x73320e64…b06f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd253247a…5d1f
0x34b655…2a6f
4 touches
1 conflict
0xbd6941a1…6281
0x34b655…2a6f
3 touches
1 conflict
0x1115d26b…d273
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2b96d534…b6b5
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x0f2d78b1bb…5e7363
Audit this contract →
← previous block
·
next block →
recent activity