pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,977,842
← previous block
next block →
recent activity
Analyzing
Block #72,977,842
12 transactions · 10 stateful · 2026-05-07 07:17:03 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,977,842
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x67098489
#3
execute
#4
updateDataFeedsValuesPartial
#5
setData
#7
forward
#8
0x69fc3ce7
· blocks 1
#10
0xeffdedb0
#11
0x39435dac
#6
0x0c7abd22
#9
0x69fc3ce7
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x45364cf9…65d7
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x273bb56b…c842
0xd32edf…ff58
3 touches
1 conflict
0x4bef88e0…eaca
0x3bd359…433a
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity