pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,482,361
← previous block
next block →
recent activity
Analyzing
Block #76,482,361
12 transactions · 10 stateful · 2026-05-23 13:02:28 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,482,361
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
exactInputSingle
#4
multicall
#5
0xab083028
· blocks 1
#7
0x98717539
#8
withdraw
#9
updatePriceFeedsIfNecessary
#10
updateDataFeedsValuesPartial
#11
setData
#6
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2dc020c7…0697
0xc8689a…ee79
4 touches
1 conflict
0x8cf3d245…1d0d
0x1d1325…2305
4 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
4 touches
1 conflict
0xea7ebe9d…709e
0x1d1325…2305
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xe2e94dfa…5026
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x99a4d286…ad43
0xa6afd3…d132
4 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:
Perpl: Settlement / Helper
1 conflict on slot
0x2dc020c71f…320697
Audit this contract →
← previous block
·
next block →
recent activity