pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,892,108
← previous block
next block →
recent activity
Analyzing
Block #70,892,108
12 transactions · 11 stateful · 2026-04-27 15:34:20 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,108
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69ef8274
#2
0xb3dd4ec4
#3
postState
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 2
#6
transfer
#7
setData
#10
0x69ef8273
#11
0x39435dac
#8
0xed82b078
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x489ea452…a633
0x065c9d…c394
4 touches
1 conflict
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x986ade47…91b9
0x065c9d…c394
3 touches
1 conflict
0xd318af39…fbae
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
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