pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,973,490
← previous block
next block →
recent activity
Analyzing
Block #95,973,490
12 transactions · 10 stateful · 2026-08-14 17:11:16 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,973,490
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
0x94defb17
· blocks 1
#6
0xcffefd2e
#7
transfer
#8
setData
· blocks 1
#10
0xfa18ed…7995
#11
0xf3d762…f46b
#5
0x94defb17
#9
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5b5d3cc…ea8f
0x968279…9342
4 touches
1 conflict
0xa5b5d3cc…ea90
0x968279…9342
4 touches
1 conflict
0xa5b5d3cc…ea91
0x968279…9342
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x11ef35af…90df
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
0xa5b5d3cca8…b6ea8f
Audit this contract →
← previous block
·
next block →
recent activity