pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,289,275
← previous block
next block →
recent activity
Analyzing
Block #96,289,275
8 transactions · 7 stateful · 2026-08-15 19:39:46 UTC
Parallelism
75
/100
Blocked
43
%
Avg conflicts / tx
0.38
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,289,275
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 2
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#3
execOrders
#5
execFwdPositionOpsV2
#7
execOrders
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
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e246445…9e0e
0x34b655…2a6f
4 touches
1 conflict
0x1e6e7167…047d
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x73670e81…2813
0x34b655…2a6f
4 touches
1 conflict
0xc01decc3…08a1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
0x0e2464459c…149e0e
Audit this contract →
← previous block
·
next block →
recent activity