pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,918,688
← previous block
next block →
recent activity
Analyzing
Block #75,918,688
10 transactions · 9 stateful · 2026-05-20 22:28:26 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,918,688
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
updatePrices
#4
0x98717539
· blocks 1
#6
redeemDelegations
#7
redeemDelegations
#8
updateDataFeedsValuesPartial
#9
setData
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74825c4e…32e9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0685b0e6…ca96
0x065c9d…c394
2 touches
0 conflicts
0x2a3d051c…00ca
0x065c9d…c394
2 touches
0 conflicts
0x5abea9c8…7f25
0x065c9d…c394
2 touches
0 conflicts
0x60f3212d…3ce5
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:
Perpl: Oracle / Operator Hub
1 conflict on slot
0x74825c4e34…8832e9
Audit this contract →
← previous block
·
next block →
recent activity