pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,571,585
← previous block
next block →
recent activity
Analyzing
Block #73,571,585
7 transactions · 7 stateful · 2026-05-10 01:07:00 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,571,585
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#4
addLiquidity
#5
setData
#6
0x69ffdaab
#2
0x0c7abd22
· blocks 1
#3
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x580c6fe7…0fe4
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x125c93f2…97ef
0xd32edf…ff58
3 touches
1 conflict
0x2a823462…e0d2
0x065c9d…c394
2 touches
0 conflicts
0x64dd94af…c64b
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:
0x188d586d…f9ea8e
1 conflict on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity