pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,084,771
← previous block
next block →
recent activity
Analyzing
Block #96,084,771
11 transactions · 10 stateful · 2026-08-15 02:31:08 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,084,771
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOpsV2
· blocks 1
#5
0x94defb17
· blocks 1
#8
setData
#9
0x61d59c2d
#10
execOrders
#6
0x94defb17
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51b0e0df…391b
0x968279…9342
4 touches
1 conflict
0x6c3b1720…6776
0x968279…9342
4 touches
1 conflict
0x6c3b1720…6777
0x968279…9342
4 touches
1 conflict
0x6c3b1720…677a
0x968279…9342
4 touches
1 conflict
0x6c3b1720…677b
0x968279…9342
4 touches
1 conflict
0x6c3b1720…677d
0x968279…9342
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
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
0x51b0e0dfa5…ac391b
Audit this contract →
← previous block
·
next block →
recent activity