pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,731,549
← previous block
next block →
recent activity
Analyzing
Block #97,731,549
10 transactions · 10 stateful · 2026-08-20 21:32:54 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,731,549
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
0xe3a3c9cc
#4
0x5acec890
· blocks 1
#5
setData
#6
execFwdPositionOpsV2
· blocks 2
#7
execFwdPositionOpsV2
· blocks 1
#9
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
8
w2
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x758591e6…a428
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0x2000b734…5e5a
0x34b655…2a6f
4 touches
1 conflict
0x69523dd3…faa2
0x34b655…2a6f
2 touches
0 conflicts
0x9d9bed71…d466
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
3 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity