pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,799,590
← previous block
next block →
recent activity
Analyzing
Block #96,799,590
11 transactions · 10 stateful · 2026-08-17 14:26:43 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,799,590
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execOrders
· blocks 1
#3
execOrders
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
0x3f5c179b
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#7
batchUpdate
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
6
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x39f0c03f…9047
0x34b655…2a6f
2 touches
0 conflicts
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
2 touches
0 conflicts
0x707c64bb…2fa6
0x34b655…2a6f
2 touches
0 conflicts
0x7c86c81a…ca46
0x34b655…2a6f
2 touches
0 conflicts
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:
Perpl
1 conflict on slot
0x03aa8b260f…60118a
Audit this contract →
← previous block
·
next block →
recent activity