pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,018,550
← previous block
next block →
recent activity
Analyzing
Block #99,018,550
11 transactions · 11 stateful · 2026-08-25 10:21:41 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,018,550
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#3
0x8263f5d9
· blocks 1
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#9
setData
#10
execOrders
#2
updatePrices
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xa3de21c2…d179
0x065c9d…c394
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x81955a0a…29ee
0x340143…768f
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x52c17a…f6f4
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
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity