pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,023,453
← previous block
next block →
recent activity
Analyzing
Block #96,023,453
9 transactions · 8 stateful · 2026-08-14 21:22:42 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,023,453
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 3
#3
0x5acec890
#4
swap
#6
verifyOracleProofV2
#8
setData
#2
0x5acec890
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0xb07f01e3…0ad4
0x34b655…2a6f
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
2 touches
0 conflicts
0x71f35abd…6a3f
0x34b655…2a6f
2 touches
0 conflicts
0x939cdd56…00c8
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
3 conflicts on slot
0x5615326245…a221ce
Audit this contract →
← previous block
·
next block →
recent activity