pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,029,550
← previous block
next block →
recent activity
Analyzing
Block #73,029,550
12 transactions · 12 stateful · 2026-05-07 13:01:11 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,029,550
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
addLiquidity
#4
0x69fc8d8e
#5
0x98717539
· blocks 1
#6
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#11
0x39435dac
#2
0x0c7abd22
· blocks 1
#10
0x39435dac
#7
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
7
w2
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x879c8d1b…97c2
0x1b6862…e19c
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x157b6348…8604
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0xddf8039f…177b
0xd32edf…ff58
3 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:
0x1b68626d…2de19c
1 conflict on slot
0x879c8d1b0f…4497c2
Audit this contract →
← previous block
·
next block →
recent activity