pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,523,043
← previous block
next block →
recent activity
Analyzing
Block #96,523,043
9 transactions · 9 stateful · 2026-08-16 15:15:48 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,523,043
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
#5
0x94defb17
· blocks 1
#8
setData
#6
0x94defb17
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91cd62de…e37f
0x968279…9342
4 touches
1 conflict
0x0b2bf6fd…ca4a
0x968279…9342
4 touches
1 conflict
0x0b2bf6fd…ca4c
0x968279…9342
4 touches
1 conflict
0x91cd62de…e37c
0x968279…9342
4 touches
1 conflict
0x91cd62de…e37d
0x968279…9342
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
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
0x91cd62de97…c5e37f
Audit this contract →
← previous block
·
next block →
recent activity