pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,514,086
← previous block
next block →
recent activity
Analyzing
Block #96,514,086
9 transactions · 7 stateful · 2026-08-16 14:30:45 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,514,086
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execFwdPositionOpsV2
#4
0x94defb17
· blocks 1
#6
execFwdPositionOpsV2
#7
setData
#8
0x61d59c2d
#3
execFwdPositionOpsV2
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d7e3ea5…4f49
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x06e95bb2…aed7
0x968279…9342
4 touches
1 conflict
0x06e95bb2…aed8
0x968279…9342
4 touches
1 conflict
0x06e95bb2…aeda
0x968279…9342
4 touches
1 conflict
0x8d7e3ea5…4f42
0x968279…9342
4 touches
1 conflict
0x8d7e3ea5…4f43
0x968279…9342
4 touches
1 conflict
0x8d7e3ea5…4f46
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
0x8d7e3ea5d8…b54f49
Audit this contract →
← previous block
·
next block →
recent activity