pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,533,535
← previous block
next block →
recent activity
Analyzing
Block #73,533,535
14 transactions · 13 stateful · 2026-05-09 20:54:22 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,533,535
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4ec9f7a2
#2
execute
#3
exactInputSingle
#4
exactInputSingle
#5
execute
#6
0xa96df62f
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x0c7abd22
· blocks 1
#11
0x69ff9f76
#12
0x39435dac
· blocks 1
#10
0x0c7abd22
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xc3483764…f297
0x1b6862…e19c
4 touches
1 conflict
0x401be839…8ac0
0x34b655…2a6f
4 touches
1 conflict
0x42deeec2…4566
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0x64461c10…e86d
0x34b655…2a6f
4 touches
1 conflict
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…000013
Audit this contract →
← previous block
·
next block →
recent activity