pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,960,636
← previous block
next block →
recent activity
Analyzing
Block #73,960,636
9 transactions · 7 stateful · 2026-05-11 20:33:11 UTC
Parallelism
56
/100
Blocked
43
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,960,636
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0xec2bd3f2
· blocks 3
#7
updateDataFeedsValuesPartial
#8
setData
#4
0x6df9e92b
· blocks 2
#5
0x6df9e92b
· blocks 1
#6
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x7b1b74a7…9206
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x41be85…e2bd
6 touches
3 conflicts
0x00000000…0001
0x41be85…e2bd
6 touches
3 conflicts
0x072430d8…35ad
0xed8924…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0xed8924…7777
6 touches
3 conflicts
0xb2c177ea…a418
0x065c9d…c394
2 touches
0 conflicts
0xf2f7c61f…a067
0x065c9d…c394
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:
0x3bd359c1…15433a
6 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity