pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,296,605
← previous block
next block →
recent activity
Analyzing
Block #72,296,605
10 transactions · 7 stateful · 2026-05-04 03:38:20 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,605
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f81524
· blocks 1
#3
0x9036287a
· blocks 1
#4
0x98717539
#5
0x98717539
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x69f81524
#2
0x69f81524
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
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
4 touches
1 conflict
0xf5846bf7…4b69
0x065c9d…c394
4 touches
1 conflict
0x84094503…5976
0x065c9d…c394
3 touches
1 conflict
0x08012a78…50c2
0x065c9d…c394
2 touches
0 conflicts
0x11b9474e…f282
0x065c9d…c394
2 touches
0 conflicts
0x5ea474f4…9697
0x065c9d…c394
2 touches
0 conflicts
0x94d284f6…ef55
0x065c9d…c394
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