pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,092,839
← previous block
next block →
recent activity
Analyzing
Block #80,092,839
8 transactions · 5 stateful · 2026-06-09 06:27:56 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,092,839
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
forward
#3
setData
#4
0xe2c6a8…d30a
#5
0xfd0fa9…7ab6
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0xc85f42b6…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6a15f784…10b2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x73f2022f…8ba2
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
2 touches
0 conflicts
0xd734d247…d36b
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
Perpl
1 conflict on slot
0xc09c342215…393c8b
Audit this contract →
← previous block
·
next block →
recent activity