pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,382,900
← previous block
next block →
recent activity
Analyzing
Block #73,382,900
10 transactions · 9 stateful · 2026-05-09 04:12:03 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,382,900
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 1
#6
0xe9316489
#7
0xeffdedb0
#8
setData
#9
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xfbce0040…02ae
0xd32edf…ff58
3 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
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
0x0000000000…00001e
Audit this contract →
← previous block
·
next block →
recent activity