pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,646,286
← previous block
next block →
recent activity
Analyzing
Block #98,646,286
11 transactions · 8 stateful · 2026-08-24 02:57:31 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,646,286
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
· blocks 1
#3
0x59558d29
#4
aggregate3
#5
placeAndExecuteMarketSell
#6
placeAndExecuteMarketSell
#7
placeAndExecuteMarketSell
#9
execFwdPositionOpsV2
#10
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd1306ad…f1b8
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x2392d2…795c
2 touches
0 conflicts
0x307d7327…3971
0x34b655…2a6f
2 touches
0 conflicts
0x6771eae2…7014
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0xb688ed23…1cf3
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
0xcd1306adf3…44f1b8
Audit this contract →
← previous block
·
next block →
recent activity