pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,310,159
← previous block
next block →
recent activity
Analyzing
Block #72,310,159
9 transactions · 7 stateful · 2026-05-04 05:08:39 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,310,159
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f82a4f
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
· blocks 1
#4
forward
#5
0xed82b078
· blocks 1
#7
0x69f82a4f
#8
setData
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b6b8b2f…29e5
0x065c9d…c394
2 touches
0 conflicts
0x34c72c1c…401e
0x065c9d…c394
2 touches
0 conflicts
0x4a5f04b9…0134
0x065c9d…c394
2 touches
0 conflicts
0x564c8f0b…88fa
0x065c9d…c394
2 touches
0 conflicts
0x6bf84d55…8756
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity