pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,124,591
← previous block
next block →
recent activity
Analyzing
Block #96,124,591
11 transactions · 11 stateful · 2026-08-15 05:51:25 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,124,591
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
execFwdPositionOpsV2
#4
setData
#5
execOrders
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbb44cedd…c666
0x34b655…2a6f
4 touches
1 conflict
0xac70fd78…de55
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x511a7372…8228
0x34b655…2a6f
2 touches
0 conflicts
0x5692e125…1727
0x34b655…2a6f
2 touches
0 conflicts
0x67bfbc55…7b2f
0x34b655…2a6f
2 touches
0 conflicts
0x7b481037…3457
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity