pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,697,343
← previous block
next block →
recent activity
Analyzing
Block #73,697,343
11 transactions · 9 stateful · 2026-05-10 15:10:31 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,697,343
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
execute
#3
0xe0de3ed7
#4
updateDataFeedsValuesPartial
#5
0x39435dac
#6
0x98717539
#7
setData
#8
0x0c7abd22
· blocks 1
#9
0x6a00a05e
#10
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa93044ee…5ce6
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2ac7f66e…e903
0x34b655…2a6f
2 touches
0 conflicts
0x742436a7…c4d4
0x34b655…2a6f
2 touches
0 conflicts
0x82134a21…d208
0x34b655…2a6f
2 touches
0 conflicts
0x885efce3…7496
0x34b655…2a6f
2 touches
0 conflicts
0xad0e9509…895d
0x34b655…2a6f
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:
0xd32edf66…9fff58
1 conflict on slot
0xa93044ee47…2c5ce6
Audit this contract →
← previous block
·
next block →
recent activity