pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,859,578
← previous block
next block →
recent activity
Analyzing
Block #72,859,578
11 transactions · 10 stateful · 2026-05-06 18:09:55 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,859,578
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x719d975a
· blocks 1
#3
0x13572d0b
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
· blocks 2
#9
0xeffdedb0
#10
setData
#2
0xff401d8f
#7
0x0c7abd22
· blocks 1
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x903ec61f…3b15
0xd32edf…ff58
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2fb6ddd2…b2a4
0x000000…012a
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xaa625301…4537
0x000000…012a
2 touches
0 conflicts
0x00000000…0000
0x5e5e5f…7924
2 touches
0 conflicts
0x00000000…0002
0x5e5e5f…7924
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:
0xd32edf66…9fff58
3 conflicts on slot
0x903ec61f97…913b15
Audit this contract →
← previous block
·
next block →
recent activity