pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,202,100
← previous block
next block →
recent activity
Analyzing
Block #73,202,100
23 transactions · 20 stateful · 2026-05-08 08:09:21 UTC
Parallelism
83
/100
Blocked
50
%
Avg conflicts / tx
0.7
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,202,100
· 23 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#6
0x69fd9aa9
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updatePrices
· blocks 1
#11
0x39435dac
· blocks 2
#12
0xe7be4706
· blocks 1
#13
0xe7be4706
#15
0x98717539
· blocks 2
#19
0x69fd9aa9
#20
0xeffdedb0
#21
setData
#2
0x0c7abd22
· blocks 2
#4
execute_route
#10
updatePrices
#16
0x98717539
· blocks 2
#3
0x0c7abd22
· blocks 2
#17
0x98717539
#18
0x5339c59f
#22
0x39435dac
#5
0x575c0012
#14
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w1
5
w3
9
w0
10
w1
11
w0
12
w0
14
w3
15
w0
16
w1
17
w2
18
w2
22
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x91220b8f…7a03
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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:
0x3bd359c1…15433a
3 conflicts on slot
0xdd70bea3b0…701ffe
Audit this contract →
← previous block
·
next block →
recent activity