pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,739,409
← previous block
next block →
recent activity
Analyzing
Block #97,739,409
12 transactions · 11 stateful · 2026-08-20 22:12:27 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,739,409
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
execOrders
#3
execOrders
· blocks 1
#4
0x6e1f3a01
#5
execPerpOps
#6
execPerpOps
#7
0x5acec890
· blocks 1
#9
forward
#10
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w0
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x91132a87…2232
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1b8c6ae2…d4cb
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
0x34b655…2a6f
2 touches
0 conflicts
0x247c79f2…e698
0x34b655…2a6f
2 touches
0 conflicts
0x2f3172c3…6625
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
0x676f9f01ee…dea8ac
Audit this contract →
← previous block
·
next block →
recent activity