pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,597,943
← previous block
next block →
recent activity
Analyzing
Block #84,597,943
10 transactions · 9 stateful · 2026-06-30 03:19:07 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,597,943
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
0x0c7abd22
#2
0xab083028
· blocks 1
#4
updatePrices
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#3
0xab083028
#5
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x042f72c4…d6a2
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0xcc434d2d…0be5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
Monad: Staking
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity