pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,360,150
← previous block
next block →
recent activity
Analyzing
Block #73,360,150
11 transactions · 9 stateful · 2026-05-09 01:40:40 UTC
Parallelism
55
/100
Blocked
44
%
Avg conflicts / tx
0.64
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,360,150
· 11 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute
#4
0x98717539
#5
updateDataFeedsValuesPartial
#9
0xeffdedb0
#10
setData
#2
0x0c7abd22
· blocks 3
#6
0xed82b078
· blocks 2
#7
0xed82b078
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
7
w3
8
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21d8e673…067f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xcb7e3b06…4a3f
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
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
6 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity