pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,296,418
← previous block
next block →
recent activity
Analyzing
Block #95,296,418
13 transactions · 10 stateful · 2026-08-12 08:19:59 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,296,418
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
commitVerification
#2
commitVerification
#3
commitVerification
#4
execPerpOps
#5
execPerpOps
#6
0x000000b2
#7
execFwdPositionOps
· blocks 1
#9
0x94defb17
· blocks 1
#11
updateDataFeedsValuesPartial
#12
setData
#8
execFwdPositionOps
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4022fca4…ef34
0x968279…9342
4 touches
1 conflict
0x20fcc560…433f
0x968279…9342
4 touches
1 conflict
0x20fcc560…4340
0x968279…9342
4 touches
1 conflict
0x20fcc560…4343
0x968279…9342
4 touches
1 conflict
0x20fcc560…4344
0x968279…9342
4 touches
1 conflict
0x20fcc560…4346
0x968279…9342
4 touches
1 conflict
0x4022fca4…ef31
0x968279…9342
4 touches
1 conflict
0x4022fca4…ef32
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0x4022fca4e2…b7ef34
Audit this contract →
← previous block
·
next block →
recent activity