pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,091
← previous block
next block →
recent activity
Analyzing
Block #70,878,091
8 transactions · 8 stateful · 2026-04-27 14:01:04 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,091
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6463ffd1
· blocks 1
#4
relay
#5
setData
#6
0x39435dac
· blocks 1
#3
0x6463ffd1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0de56a7e…728f
0x065c9d…c394
4 touches
1 conflict
0x2f9e01e1…e43e
0x065c9d…c394
4 touches
1 conflict
0xa81b6f69…c15c
0x065c9d…c394
4 touches
1 conflict
0xf8e87842…51f7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity