pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,323
← previous block
next block →
recent activity
Analyzing
Block #71,421,323
11 transactions · 6 stateful · 2026-04-30 02:18:51 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,323
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
· blocks 1
#3
approve
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
forward
#7
setData
#8
0x0ae2f0…e5ca
#9
0xcccf3e…0cf8
#10
0x663e45…1fc7
#2
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4ab4c621…4e8c
0x065c9d…c394
2 touches
0 conflicts
0x4ed9c145…2d7d
0x065c9d…c394
2 touches
0 conflicts
0xe461d859…a5de
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:
0x34b6552d…112a6f
1 conflict on slot
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity