pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,681,141
← previous block
next block →
recent activity
Analyzing
Block #73,681,141
9 transactions · 7 stateful · 2026-05-10 13:21:22 UTC
Parallelism
56
/100
Blocked
43
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,681,141
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
#2
0x16040cc9
· blocks 3
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
setData
#3
0x16040cc9
· blocks 2
#4
0x16040cc9
· blocks 1
#5
0x16040cc9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95e37fef…f5bf
0x3ec731…7777
8 touches
6 conflicts
0x00000000…0000
0x877f30…7c0b
8 touches
6 conflicts
0x00000000…0001
0x877f30…7c0b
8 touches
6 conflicts
0x00000000…0003
0x877f30…7c0b
8 touches
6 conflicts
0xe75ca10f…d28a
0x3bd359…433a
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x71cd5bd2…8c51
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:
0x3ec73109…ff7777
6 conflicts on slot
0x95e37fefc9…23f5bf
Audit this contract →
← previous block
·
next block →
recent activity