pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,167,020
← previous block
next block →
recent activity
Analyzing
Block #76,167,020
10 transactions · 7 stateful · 2026-05-22 02:02:46 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,167,020
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
exactInputSingle
#6
0x6df9e92b
· blocks 1
#8
setData
#9
0x1f620c…d175
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x30611e…d8d9
4 touches
1 conflict
0x00000000…0002
0x30611e…d8d9
4 touches
1 conflict
0x44ad89ba…cf83
0x25d593…7777
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x24cfe713…0f91
0x25d593…7777
4 touches
1 conflict
0xe3ee7f9e…f356
0x3bd359…433a
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
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:
0x30611e93…1ad8d9
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity