pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,986,057
← previous block
next block →
recent activity
Analyzing
Block #73,986,057
13 transactions · 9 stateful · 2026-05-11 23:23:29 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,986,057
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x1ffa3c9b
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0xf5bee0…6d77
#7
0xe15e7f…0758
#8
setData
#9
0x39435dac
#10
0x39435dac
#11
0x39435dac
#12
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0906d702…b995
0x065c9d…c394
2 touches
0 conflicts
0x34a97c8f…76b3
0x065c9d…c394
2 touches
0 conflicts
0xb7571319…5147
0x065c9d…c394
2 touches
0 conflicts
0xd0d35893…4a2d
0x065c9d…c394
2 touches
0 conflicts
0xdc82a7b4…6d5c
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity