pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,532,050
← previous block
next block →
recent activity
Analyzing
Block #97,532,050
13 transactions · 12 stateful · 2026-08-20 04:36:23 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,532,050
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x7b84f330
· blocks 1
#4
0xab083028
#5
0xab083028
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#9
redeemDelegations
#10
0x59558d29
#11
execOrders
#2
0x0c7abd22
#6
0xab083028
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w0
6
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity