pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,491,055
← previous block
next block →
recent activity
Analyzing
Block #80,491,055
13 transactions · 7 stateful · 2026-06-11 02:41:58 UTC
Parallelism
85
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,491,055
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute_route
#4
execute_route
#5
execute_route
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
forward
#10
0x6a2a20ee
#11
setData
#12
0x39435dac
#2
0x0c7abd22
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
0xbebc7c5b…373f
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x9256b810…52cb
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x19deb181…7dc2
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x1462cfa9…995d
0x010592…1c83
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
0xbebc7c5b17…b4373f
Audit this contract →
← previous block
·
next block →
recent activity