pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,257,182
← previous block
next block →
recent activity
Analyzing
Block #96,257,182
10 transactions · 10 stateful · 2026-08-15 16:58:21 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,257,182
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
execFwdPositionOpsV2
· blocks 1
#4
execOrders
#5
execOrders
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eaa3f4e…2992
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0xe624cb16…9dc0
0x34b655…2a6f
4 touches
1 conflict
0x3df0422c…fd39
0x34b655…2a6f
2 touches
0 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
2 touches
0 conflicts
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 conflicts
0x824b4c5c…a6d0
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
0x0eaa3f4efc…4f2992
Audit this contract →
← previous block
·
next block →
recent activity