pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,633,548
← previous block
next block →
recent activity
Analyzing
Block #81,633,548
12 transactions · 7 stateful · 2026-06-16 09:35:58 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,633,548
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x98717539
#6
0x64480813
#7
0xe80303…6fa1
#8
0xf19d4d…f58f
#9
0xb2c800…491b
#10
0x783acc…f340
#11
setData
#5
addSellOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa9f633f5…7480
0x065c9d…c394
2 touches
0 conflicts
0xaa5a0f58…8f0c
0x065c9d…c394
2 touches
0 conflicts
0xc6f98c66…1d44
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0xd8e41896…1a83
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
1 conflict on slot
0x52e6914362…6e95ad
Audit this contract →
← previous block
·
next block →
recent activity