pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,510,720
← previous block
next block →
recent activity
Analyzing
Block #96,510,720
7 transactions · 7 stateful · 2026-08-16 14:13:50 UTC
Parallelism
71
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,510,720
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
· blocks 1
#4
setData
#5
execOrders
· blocks 1
#3
execFwdPositionOpsV2
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0xaafc0c3d…64b6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1f704c5a…28c7
0x34b655…2a6f
2 touches
0 conflicts
0x298bdf9a…aa3e
0x34b655…2a6f
2 touches
0 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
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
0x0fb9e50cd4…5a1a35
Audit this contract →
← previous block
·
next block →
recent activity