pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,038,482
← previous block
next block →
recent activity
Analyzing
Block #96,038,482
10 transactions · 8 stateful · 2026-08-14 22:38:19 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,038,482
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
0x94defb17
· blocks 2
#8
execFwdPositionOpsV2
#9
setData
#2
0x5acec890
#6
0x94defb17
· blocks 1
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78da9e…7106
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x541ac4bb…6e38
0x968279…9342
6 touches
3 conflicts
0x541ac4bb…6e39
0x968279…9342
6 touches
3 conflicts
0x541ac4bb…6e3b
0x968279…9342
6 touches
3 conflicts
0xbf78da9e…70ff
0x968279…9342
6 touches
3 conflicts
0xbf78da9e…7100
0x968279…9342
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:
0x96827978…f09342
3 conflicts on slot
0xbf78da9e6a…777106
Audit this contract →
← previous block
·
next block →
recent activity