pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,449,206
← previous block
next block →
recent activity
Analyzing
Block #98,449,206
13 transactions · 10 stateful · 2026-08-23 09:59:00 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,449,206
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
execOrders
· blocks 1
#5
0x59558d29
#6
0x5acec890
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0x3f5c179b
#11
execOrders
#12
execOrders
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1040ff5a…d433
0x34b655…2a6f
2 touches
0 conflicts
0x1204f20c…3f98
0x34b655…2a6f
2 touches
0 conflicts
0x26c57a37…e45b
0x34b655…2a6f
2 touches
0 conflicts
0x391d75c5…b826
0x34b655…2a6f
2 touches
0 conflicts
0x4847c505…b303
0x34b655…2a6f
2 touches
0 conflicts
0x5aed1bd2…7afa
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity