pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,964,722
← previous block
next block →
recent activity
Analyzing
Block #73,964,722
10 transactions · 9 stateful · 2026-05-11 21:00:23 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,964,722
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6df9e92b
· blocks 1
#6
0x5339c59f
· blocks 1
#8
0x6a0243df
#9
setData
#5
0x6df9e92b
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7b1b74a7…9206
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x41be85…e2bd
4 touches
1 conflict
0x00000000…0001
0x41be85…e2bd
4 touches
1 conflict
0x072430d8…35ad
0xed8924…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xed8924…7777
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity