pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,704,117
← previous block
next block →
recent activity
Analyzing
Block #71,704,117
13 transactions · 10 stateful · 2026-05-01 09:45:44 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,704,117
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0c7abd22
· blocks 1
#3
0xeffdedb0
#5
0x6df9e92b
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x69f476c0
#9
setData
#10
0xfcbe55…4456
#11
0xcf8f63…cde0
#12
0x39435dac
#4
0x3f5c179b
#6
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xaa3e5ab2…fd8a
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x7131ec…7777
4 touches
1 conflict
0xd46cd782…e7f2
0x7131ec…7777
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0xc82b5c…bb3a
4 touches
1 conflict
0x00000000…0001
0xc82b5c…bb3a
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
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:
0x3bd359c1…15433a
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity