pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,496,223
← previous block
next block →
recent activity
Analyzing
Block #72,496,223
12 transactions · 10 stateful · 2026-05-05 01:48:07 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,496,223
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
deposit
#3
0x69f94cce
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
0x98717539
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x3f5c179b
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x76498d82…2995
0x000000…012a
2 touches
0 conflicts
0x00000000…000d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0016
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x07faeeb9…423a
0x1b6862…e19c
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
0x1c38946843…a16b0e
Audit this contract →
← previous block
·
next block →
recent activity