pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,922,662
← previous block
next block →
recent activity
Analyzing
Block #73,922,662
10 transactions · 7 stateful · 2026-05-11 16:20:40 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,922,662
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a020250
#2
0x6a02024f
#3
0x0c7abd22
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x397051…ee4c
#8
0xa9f0ac…4878
#9
0x39435dac
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb81
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xc30b22c2…bff0
0xd32edf…ff58
3 touches
1 conflict
0x8134ad57…769f
0x065c9d…c394
2 touches
0 conflicts
0x99b853ab…bcb0
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:
0x1b68626d…2de19c
1 conflict on slot
0xcb45d9d62a…b1cb81
Audit this contract →
← previous block
·
next block →
recent activity