pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#71,041,743
← previous block
next block →
recent activity
Analyzing
Block #71,041,743
5 transactions · 4 stateful · 2026-04-28 08:10:42 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,041,743
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6463ffd1
· blocks 1
#2
updateDataFeedsValuesPartial
#4
setData
#3
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b0b02d4…8a47
0x065c9d…c394
4 touches
1 conflict
0x3729e5de…1f68
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x555403c1…df09
0x065c9d…c394
3 touches
1 conflict
0xe7032629…9525
0x065c9d…c394
3 touches
1 conflict
0x55a99db5…9eaa
0x065c9d…c394
2 touches
1 conflict
0x133c700b…4145
0x065c9d…c394
2 touches
1 conflict
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
0x1b0b02d451…f68a47
Audit this contract →
← previous block
·
next block →
recent activity