pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,246,804
← previous block
next block →
recent activity
Analyzing
Block #76,246,804
10 transactions · 7 stateful · 2026-05-22 10:54:16 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,246,804
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#4
0xc471f1…9a2b
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
claimRewards
#8
setData
#9
0x39435dac
#3
swap
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
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x91946270…7f86
0x065c9d…c394
4 touches
1 conflict
0xd06c305e…38e6
0x065c9d…c394
3 touches
1 conflict
0xb0d92b7a…3754
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x066eb03d…4232
0x065c9d…c394
2 touches
0 conflicts
0x1303817e…d344
0x065c9d…c394
2 touches
0 conflicts
0x346974c3…adb2
0x065c9d…c394
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x0aa885fa2f…33a3d1
Audit this contract →
← previous block
·
next block →
recent activity