pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,176,841
← previous block
next block →
recent activity
Analyzing
Block #71,176,841
8 transactions · 8 stateful · 2026-04-28 23:10:33 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,176,841
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x572c8ce3
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
· blocks 1
#5
0x7c51d6cf
#6
setData
#7
0x39435dac
#4
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x357e53cc…e772
0x065c9d…c394
4 touches
1 conflict
0x84478b8d…a4c2
0x065c9d…c394
4 touches
1 conflict
0x9c7b91ee…5e71
0x065c9d…c394
4 touches
1 conflict
0xd221d591…95b8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0x8956cb26…42fa
0x73ada1…8be0
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
0x357e53cc30…77e772
Audit this contract →
← previous block
·
next block →
recent activity