pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,482,409
← previous block
next block →
recent activity
Analyzing
Block #81,482,409
14 transactions · 11 stateful · 2026-06-15 16:49:22 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,482,409
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
withdraw
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
forward
#9
0x6df9e92b
#10
0x6a302d8a
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#2
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0xff3c0315…a3e2
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000b
0x097d40…9920
2 touches
0 conflicts
0x24cfe713…0f91
0x25d593…7777
2 touches
0 conflicts
0x44ad89ba…cf83
0x25d593…7777
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: MarginAccount
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity