pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,291,086
← previous block
next block →
recent activity
Analyzing
Block #76,291,086
11 transactions · 10 stateful · 2026-05-22 15:48:47 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,291,086
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9609049f
· blocks 2
#3
exactInputSingle
#4
redeem
#5
0x5bf9264c
#6
0x5bf9264c
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#2
execute
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a995
0x188d58…ea8e
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0xeb065f2b…2c9a
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:
AUSD (AUSD)
1 conflict on slot
0x12309510bf…250ac2
Audit this contract →
← previous block
·
next block →
recent activity