pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,081,658
← previous block
next block →
recent activity
Analyzing
Block #98,081,658
13 transactions · 13 stateful · 2026-08-22 03:09:06 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,081,658
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x6ad2e98b
#3
execOrder
#4
0x59558d29
#5
updatePriceFeedsIfNecessary
#6
forward
#7
forward
#8
execFwdPositionOpsV2
#9
transferWithAuthorization
#10
setData
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1566cc31…8ee9
0x34b655…2a6f
2 touches
0 conflicts
0x2f4fd493…9935
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x86d26761…7ed4
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity