pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,343,681
← previous block
next block →
recent activity
Analyzing
Block #73,343,681
24 transactions · 20 stateful · 2026-05-08 23:51:11 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,343,681
· 24 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x575c0012
#2
0x69fe7767
· blocks 1
#4
updatePrices
#5
0x39435dac
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x5bf9264c
#9
0x5bf9264c
#10
0x98717539
#11
0xe7be4706
#12
0x0c7abd22
· blocks 4
#16
0x62be7533
#17
0xc5918880
#18
createModule
#20
0xeffdedb0
#21
setData
#23
jMMeC
#3
0x69fe7767
#13
0x0c7abd22
· blocks 3
#22
0x39435dac
#14
0x0c7abd22
· blocks 2
#15
0x0c7abd22
#19
0xa9b28aa6
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
12
w0
13
w1
14
w2
15
w3
19
w3
22
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x5c14b918…f796
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xc3483764…f29b
0x1b6862…e19c
6 touches
3 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:
0x754704bc…afb603
6 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity