pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,636,333
← previous block
next block →
recent activity
Analyzing
Block #95,636,333
11 transactions · 10 stateful · 2026-08-13 12:54:04 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,636,333
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execute
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
0x9e76c652
#7
0x6a7dbee4
#8
setData
#9
0x59558d29
#10
swapExactTokensForTokens
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34cdb3c2…96d2
0x34b655…2a6f
4 touches
1 conflict
0x8722ac78…9cfc
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x31b61a13…ca9f
0x34b655…2a6f
2 touches
0 conflicts
0x4334088a…a88c
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
0x34cdb3c2ce…9296d2
Audit this contract →
← previous block
·
next block →
recent activity