pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,289,136
← previous block
next block →
recent activity
Analyzing
Block #71,289,136
25 transactions · 19 stateful · 2026-04-29 11:37:40 UTC
Parallelism
84
/100
Blocked
42
%
Avg conflicts / tx
0.48
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,136
· 25 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#5
0x0c7abd22
#6
updatePrices
· blocks 1
#7
execute
#8
execute
#9
multicall
#11
0x98717539
· blocks 1
#12
updateDataFeedsValuesPartial
#13
0x69f1edfc
· blocks 1
#14
setData
#17
0x39435dac
#18
0x39435dac
#20
0x39435dac
#22
0x39435dac
#23
updatePrices
#24
updatePrices
#2
0x0c7abd22
· blocks 2
#10
updatePrices
#15
0x69f1edfc
#16
0x39435dac
· blocks 2
#3
0x0c7abd22
· blocks 1
#19
0x39435dac
· blocks 1
#4
0x0c7abd22
#21
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
6
w0
10
w1
11
w0
13
w0
15
w1
16
w1
19
w2
21
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8504d39…bf23
0xd32edf…ff58
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x14d1bf0e…e09d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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:
0xd32edf66…9fff58
6 conflicts on slot
0xe8504d3945…cebf23
Audit this contract →
← previous block
·
next block →
recent activity