pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,629,613
← previous block
next block →
recent activity
Analyzing
Block #81,629,613
9 transactions · 9 stateful · 2026-06-16 09:09:45 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,629,613
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x23afbff3
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x98717539
#6
0x6a311350
#7
setData
#8
0xc7e3ec2c
#2
0xab083028
· blocks 1
#5
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01926acd…1038
0x065c9d…c394
2 touches
0 conflicts
0x1b24c961…9ed1
0x065c9d…c394
2 touches
0 conflicts
0x52ad63fe…eb0a
0x065c9d…c394
2 touches
0 conflicts
0xaf7c4e2f…2922
0x065c9d…c394
2 touches
0 conflicts
0xced78f1d…0eb5
0x065c9d…c394
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
3 conflicts on slot
0xce827910a4…82ff22
Audit this contract →
← previous block
·
next block →
recent activity