pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,279,335
← previous block
next block →
recent activity
Analyzing
Block #95,279,335
8 transactions · 7 stateful · 2026-08-12 06:53:44 UTC
Parallelism
63
/100
Blocked
43
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,279,335
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 3
#3
0x57368ddf
#6
setData
#7
withdraw
#2
execFwdPositionOps
· blocks 1
#5
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0xc576a23c…4aba
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xb0608dfe…083d
0x34b655…2a6f
4 touches
1 conflict
0xe40066a0…3b48
0x34b655…2a6f
4 touches
1 conflict
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
0x89999c1534…effdac
Audit this contract →
← previous block
·
next block →
recent activity