pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,065,799
← previous block
next block →
recent activity
Analyzing
Block #71,065,799
9 transactions · 9 stateful · 2026-04-28 10:50:52 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,065,799
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x98717539
#4
0x6463ffd1
· blocks 1
#6
updateDataFeedsValuesPartial
#7
claimRewards
#8
setData
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fe7615a…1162
0x065c9d…c394
4 touches
1 conflict
0x9c46a1a1…2f7f
0x065c9d…c394
4 touches
1 conflict
0xd28d4f05…f4fa
0x065c9d…c394
4 touches
1 conflict
0xd3d7b465…e79c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
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:
0x065c9d28…a9c394
1 conflict on slot
0x3fe7615a0c…cb1162
Audit this contract →
← previous block
·
next block →
recent activity