pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,064,990
← previous block
next block →
recent activity
Analyzing
Block #71,064,990
7 transactions · 6 stateful · 2026-04-28 10:45:28 UTC
Parallelism
43
/100
Blocked
50
%
Avg conflicts / tx
0.71
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,064,990
· 7 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x42dd8743
· blocks 2
#2
updateDataFeedsValuesPartial
#6
setData
#3
0x6463ffd1
· blocks 2
#4
0x0c7abd22
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x1d835484…12cf
0x065c9d…c394
3 touches
1 conflict
0xd3904135…abbf
0x065c9d…c394
3 touches
1 conflict
0x0e4fcaad…df25
0xd32edf…ff58
3 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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x92d610a6f9…379a40
Audit this contract →
← previous block
·
next block →
recent activity