pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,592,639
← previous block
next block →
recent activity
Analyzing
Block #93,592,639
11 transactions · 10 stateful · 2026-08-06 09:03:16 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,592,639
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
· blocks 1
#4
placeAndExecuteMarketBuy
· blocks 1
#6
execFwdPositionOps
#7
0x57368ddf
#8
0x6a744e4c
#9
setData
#10
0x36326531
#3
execFwdPositionOps
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x679122e7…7e9f
0x851145…3f07
3 touches
1 conflict
0x05b26de9…0fd8
0x34b655…2a6f
2 touches
0 conflicts
0x0b3cfc56…2a4a
0x34b655…2a6f
2 touches
0 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x29b23b5b…93ee
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
0x69a45f39d6…c739aa
Audit this contract →
← previous block
·
next block →
recent activity