pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,561,256
← previous block
next block →
recent activity
Analyzing
Block #98,561,256
11 transactions · 11 stateful · 2026-08-23 19:34:46 UTC
Parallelism
82
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,561,256
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
setData
#7
forward
#8
execFwdPositionOpsV2
· blocks 1
#10
execOrders
#2
0x8263f5d9
#6
0xed82b078
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52220806…53a1
0x065c9d…c394
4 touches
1 conflict
0xb949a223…b426
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x52220806b4…6e53a1
Audit this contract →
← previous block
·
next block →
recent activity