pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,395,621
← previous block
next block →
recent activity
Analyzing
Block #95,395,621
12 transactions · 11 stateful · 2026-08-12 16:42:31 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,395,621
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
· blocks 1
#2
swapExactTokenForYt
#3
execPerpOps
#4
execPerpOps
#6
0x5acec890
#7
execFwdPositionOps
#8
transfer
· blocks 1
#10
setData
#11
0x59558d29
#5
dagSwapByOrderId
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x00000000…0003
0x850662…52d0
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
0x899a0e35…c279
0x0898c3…f274
2 touches
0 conflicts
0xdb1960a0…7eb8
0x0898c3…f274
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:
Wrapped MON (WMON)
1 conflict on slot
0x63f5c02f70…9e6853
Audit this contract →
← previous block
·
next block →
recent activity