pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,215,944
← previous block
next block →
recent activity
Analyzing
Block #73,215,944
12 transactions · 11 stateful · 2026-05-08 09:41:22 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,215,944
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
removeLiquidity
#3
0x52f07cf9
· blocks 1
#5
updatePrices
#6
execOrders
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
0x69fdb03a
#10
0xeffdedb0
#11
setData
#4
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0471531c…62e6
0x065c9d…c394
2 touches
0 conflicts
0x93d40eed…5d8f
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
2 touches
0 conflicts
0xfdae7e5f…4865
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:
Wrapped MON (WMON)
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity