pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,288,381
← previous block
next block →
recent activity
Analyzing
Block #72,288,381
11 transactions · 8 stateful · 2026-05-04 02:43:09 UTC
Parallelism
82
/100
Blocked
38
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,288,381
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 2
#3
0x69f80835
· blocks 1
#5
0x69f80835
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
setData
#10
0xad43e7…b96a
#2
0xce1e7030
#4
0x69f80835
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e71984…ae90
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x8b7d425c…0fd5
0x065c9d…c394
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xf95b6d36…7441
0x065c9d…c394
3 touches
1 conflict
0x6dcb1de8…485d
0x065c9d…c394
3 touches
1 conflict
0xc477894b…3523
0x065c9d…c394
3 touches
1 conflict
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
0x74e71984e8…06ae90
Audit this contract →
← previous block
·
next block →
recent activity