pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,860,808
← previous block
next block →
recent activity
Analyzing
Block #72,860,808
9 transactions · 8 stateful · 2026-05-06 18:18:07 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,860,808
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x0c7abd22
· blocks 1
#6
0xeffdedb0
#7
0x39435dac
#8
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xccf5ea30…7ded
0xd32edf…ff58
3 touches
1 conflict
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0xbf105daf…cab9
0x2185cd…21c7
2 touches
0 conflicts
0x001befaf…7524
0x2ae0cf…3d4e
2 touches
0 conflicts
0x06f46c21…b503
0x2ae0cf…3d4e
2 touches
0 conflicts
0x122034dc…fa3b
0x2ae0cf…3d4e
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
0xcb45d9d62a…b1cb84
Audit this contract →
← previous block
·
next block →
recent activity