pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,296,340
← previous block
next block →
recent activity
Analyzing
Block #72,296,340
9 transactions · 8 stateful · 2026-05-04 03:36:35 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,340
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f814ba
#2
0x9036287a
· blocks 1
#3
updateDataFeedsValuesPartial
#5
forward
#6
forward
#7
0x69f814ba
#8
setData
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x22473194…66f7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5b127bd7…ee7c
0x065c9d…c394
4 touches
1 conflict
0xf5846bf7…4b69
0x065c9d…c394
3 touches
1 conflict
0x5f0770c4…06ec
0x065c9d…c394
3 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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
0xbbee74c2e7…6e567a
Audit this contract →
← previous block
·
next block →
recent activity