pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,286,019
← previous block
next block →
recent activity
Analyzing
Block #72,286,019
9 transactions · 8 stateful · 2026-05-04 02:27:17 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,286,019
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
forward
#4
forward
#5
0x69f8047d
· blocks 1
#7
setData
#8
modifyLiquidities
#6
0x69f8047d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x068f120a…e845
0x065c9d…c394
2 touches
0 conflicts
0x2d487a0a…89b8
0x065c9d…c394
2 touches
0 conflicts
0xb48e993c…0fd2
0x065c9d…c394
2 touches
0 conflicts
0xb616ad12…0f16
0x065c9d…c394
2 touches
0 conflicts
0xe0ada570…8dc9
0x065c9d…c394
2 touches
0 conflicts
0x3ab0a69b…4fba
0x188d58…ea8e
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity