pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,099,264
← previous block
next block →
recent activity
Analyzing
Block #72,099,264
11 transactions · 9 stateful · 2026-05-03 05:36:32 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,099,264
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67a7528c
· blocks 1
#2
0x69f6df58
#3
updatePrices
#4
updatePrices
#5
0x98717539
· blocks 1
#6
0x98717539
#8
updateDataFeedsValuesPartial
#9
setData
#7
0x3f5c179b
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xbf04f37d…85f2
0x2a68ba…90c5
2 touches
0 conflicts
0x06b3fede…7ccc
0x34b655…2a6f
2 touches
0 conflicts
0x3254d19b…f714
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x3b2d25d4…fb40
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
0xadac4a860c…a3c2bc
Audit this contract →
← previous block
·
next block →
recent activity