pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,214,062
← previous block
next block →
recent activity
Analyzing
Block #72,214,062
8 transactions · 6 stateful · 2026-05-03 18:23:43 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,214,062
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x1a945f9c
#3
0x9036287a
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcada175e…40a0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7305bc22…d366
0x065c9d…c394
3 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x116d4e0a…6c0c
0x1efe02…37d6
2 touches
0 conflicts
0x47915b09…74ce
0x1efe02…37d6
2 touches
0 conflicts
0x4b18d9ab…5581
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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
0xcada175e3d…de40a0
Audit this contract →
← previous block
·
next block →
recent activity