pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,289,430
← previous block
next block →
recent activity
Analyzing
Block #71,289,430
11 transactions · 10 stateful · 2026-04-29 11:39:37 UTC
Parallelism
73
/100
Blocked
40
%
Avg conflicts / tx
0.45
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,430
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#4
multicall
#5
updateDataFeedsValuesPartial
#7
0x69f1ee70
#8
setData
#9
0x39435dac
· blocks 1
#2
0x8d01c5c8
· blocks 1
#6
0x20601463
#10
0x39435dac
#3
0xbc3ec4c2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x8f313589…99bf
0x065c9d…c394
2 touches
0 conflicts
0x9d15a471…afa7
0x065c9d…c394
2 touches
0 conflicts
0xa9d62c78…3fa9
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000d
0x1b6862…e19c
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:
0x1b68626d…2de19c
3 conflicts on slot
0x0000000000…000012
Audit this contract →
← previous block
·
next block →
recent activity