pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,317,085
← previous block
next block →
recent activity
Analyzing
Block #72,317,085
10 transactions · 7 stateful · 2026-05-04 05:54:45 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,317,085
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x711663…8b44
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5cc41bfa…6a9a
0x34b655…2a6f
2 touches
0 conflicts
0x73d62b4d…1bec
0x34b655…2a6f
2 touches
0 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…641c
0x34b655…2a6f
2 touches
0 conflicts
0xd895ee0b…d301
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity