pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,707,347
← previous block
next block →
recent activity
Analyzing
Block #80,707,347
12 transactions · 10 stateful · 2026-06-12 02:45:05 UTC
Parallelism
75
/100
Blocked
30
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,707,347
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updatePrices
· blocks 1
#6
updatePrices
#7
updatePrices
#8
0x3f5c179b
#10
0x6a2b7329
#11
setData
#2
0x0c7abd22
· blocks 1
#5
updatePrices
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0xfe1362cf…bb85
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x1504aa7b…24ad
0xa6afd3…d132
4 touches
1 conflict
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:
0xa6afd386…b0d132
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity