pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,301,315
← previous block
next block →
recent activity
Analyzing
Block #72,301,315
9 transactions · 7 stateful · 2026-05-04 04:09:43 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,301,315
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x9036287a
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
forward
#8
setData
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca14ae2e…a7a3
0x065c9d…c394
4 touches
1 conflict
0xf2ca305d…2145
0x065c9d…c394
3 touches
1 conflict
0xfabba1da…f640
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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:
0x065c9d28…a9c394
1 conflict on slot
0xf823e97fa0…262ee6
Audit this contract →
← previous block
·
next block →
recent activity