pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,689,911
← previous block
next block →
recent activity
Analyzing
Block #97,689,911
11 transactions · 10 stateful · 2026-08-20 18:01:37 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,689,911
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
0xab083028
#4
execOrder
· blocks 1
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
0x59558d29
#5
execOrder
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bc43347…93d4
0x34b655…2a6f
4 touches
1 conflict
0x69352f9f…5449
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22e35fe3…1f6b
0x34b655…2a6f
2 touches
0 conflicts
0x2364dac9…7a56
0x34b655…2a6f
2 touches
0 conflicts
0x3c144d40…9554
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
0x0bc433477d…9e93d4
Audit this contract →
← previous block
·
next block →
recent activity