pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,437,786
← previous block
next block →
recent activity
Analyzing
Block #96,437,786
13 transactions · 13 stateful · 2026-08-16 08:06:40 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,437,786
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
execOrders
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
0x94defb17
· blocks 2
#9
forward
#11
transfer
#12
setData
#8
0x94defb17
· blocks 1
#10
resolve
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xda5bd818…0bcf
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x4f45cc5f…eb3f
0x968279…9342
4 touches
1 conflict
0x4f45cc5f…eb40
0x968279…9342
4 touches
1 conflict
0x4f45cc5f…eb42
0x968279…9342
4 touches
1 conflict
0xda5bd818…0bc9
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
3 conflicts on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity