pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,136,139
← previous block
next block →
recent activity
Analyzing
Block #96,136,139
11 transactions · 9 stateful · 2026-08-15 06:49:33 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,136,139
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0xcbbdb31a
#3
0xab083028
#4
execOrder
· blocks 1
#5
0x5acec890
· blocks 1
#7
execFwdPositionOpsV2
#9
verifyOracleProofV2
#10
setData
#6
0x5acec890
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0x4646752b…faf3
0x111111…db61
2 touches
0 conflicts
0x00000000…0000
0x2970fd…1fc2
2 touches
0 conflicts
0x00000000…000a
0x2d8bbb…026a
2 touches
0 conflicts
0x00000000…0005
0x3249df…c0f6
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity