pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,513,774
← previous block
next block →
recent activity
Analyzing
Block #73,513,774
20 transactions · 12 stateful · 2026-05-09 18:43:03 UTC
Parallelism
85
/100
Blocked
42
%
Avg conflicts / tx
0.35
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,513,774
· 20 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#5
updatePrices
· blocks 2
#8
0xe7be4706
#9
0x5bf9264c
#10
0x5bf9264c
#11
updateDataFeedsValuesPartial
#12
0xe7be4706
#13
setData
#14
createModule
#15
0xc543fd…0631
#16
0x6b3994…c546
#17
0xa50349…4308
#18
0x39ec25…1e64
#19
0xb29d78…97f1
#2
0x0c7abd22
· blocks 2
#6
updatePrices
· blocks 1
#3
0x0c7abd22
#4
0x575c0012
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w2
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x0c562962…8276
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
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:
0xab35264b…1cfa38
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity