pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,065,676
← previous block
next block →
recent activity
Analyzing
Block #71,065,676
9 transactions · 9 stateful · 2026-04-28 10:50:03 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,065,676
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
relay
#4
forward
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
· blocks 1
#2
0x6463ffd1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10b5ff2e…ea9b
0x065c9d…c394
2 touches
0 conflicts
0x21b3c0ff…2a6b
0x065c9d…c394
2 touches
0 conflicts
0x222ae6f9…c592
0x065c9d…c394
2 touches
0 conflicts
0x9ba43a03…c3af
0x065c9d…c394
2 touches
0 conflicts
0xef119265…9eb8
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
0x15c9b5bf08…57f732
Audit this contract →
← previous block
·
next block →
recent activity