pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,307,777
← previous block
next block →
recent activity
Analyzing
Block #96,307,777
10 transactions · 10 stateful · 2026-08-15 21:12:49 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,307,777
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
· blocks 1
#7
0x94defb17
· blocks 1
#8
0x94defb17
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf89542f…7537
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x25d1e3f7…0437
0x968279…9342
4 touches
1 conflict
0x25d1e3f7…0438
0x968279…9342
4 touches
1 conflict
0x25d1e3f7…043a
0x968279…9342
4 touches
1 conflict
0xaf89542f…7530
0x968279…9342
4 touches
1 conflict
0xaf89542f…7531
0x968279…9342
4 touches
1 conflict
0xaf89542f…7534
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
0xaf89542f64…617537
Audit this contract →
← previous block
·
next block →
recent activity