pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,564,862
← previous block
next block →
recent activity
Analyzing
Block #95,564,862
10 transactions · 8 stateful · 2026-08-13 06:54:34 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,564,862
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
0x94defb17
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a7d6aa2
#6
setData
· blocks 1
#8
0x1fa221…5068
#9
0x59558d29
#3
0x94defb17
#7
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcee3ff5…c6d8
0x968279…9342
4 touches
1 conflict
0x8daff965…05ca
0x968279…9342
4 touches
1 conflict
0x8daff965…05cc
0x968279…9342
4 touches
1 conflict
0xdcee3ff5…c6d2
0x968279…9342
4 touches
1 conflict
0xdcee3ff5…c6d3
0x968279…9342
4 touches
1 conflict
0xdcee3ff5…c6d6
0x968279…9342
4 touches
1 conflict
0xdcee3ff5…c6d7
0x968279…9342
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
0xdcee3ff537…bec6d8
Audit this contract →
← previous block
·
next block →
recent activity