pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,286,569
← previous block
next block →
recent activity
Analyzing
Block #98,286,569
9 transactions · 8 stateful · 2026-08-22 20:20:44 UTC
Parallelism
67
/100
Blocked
50
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,286,569
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x6ad2e98b
#4
execOrder
· blocks 3
#8
0x7b84f330
#2
0xab083028
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
6 touches
3 conflicts
0x554e66db…29d8
0x34b655…2a6f
5 touches
3 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
4 touches
1 conflict
0x58737d82…26ba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…641f
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
3 conflicts on slot
0xd66696e0dc…230842
Audit this contract →
← previous block
·
next block →
recent activity