pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,099,202
← previous block
next block →
recent activity
Analyzing
Block #72,099,202
9 transactions · 7 stateful · 2026-05-03 05:36:07 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,099,202
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x2e3c1e40
· blocks 1
#3
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
setData
#8
0x36326531
#4
0xe1154a09
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xeec8a7…14df
4 touches
1 conflict
0xf408c623…5ddf
0xeec8a7…14df
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23529e13…6f25
0x34b655…2a6f
2 touches
0 conflicts
0x2827ae77…4368
0x34b655…2a6f
2 touches
0 conflicts
0x2fad73a1…ae09
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x69f0d775…13f5
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:
0xeec8a75a…8e14df
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity