pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,256,267
← previous block
next block →
recent activity
Analyzing
Block #76,256,267
9 transactions · 8 stateful · 2026-05-22 11:57:08 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,256,267
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbb5d006a
· blocks 1
#3
updatePrices
#4
0x98717539
#5
0x6df9e92b
#6
updateDataFeedsValuesPartial
#7
setData
#8
exactInputSingle
#2
0xbb5d006a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ee00353…b4fe
0x541997…f5a0
4 touches
1 conflict
0x11835075…38e5
0x541997…f5a0
4 touches
1 conflict
0x11835075…38e6
0x541997…f5a0
4 touches
1 conflict
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0002
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
2 touches
0 conflicts
0xf0c05263…9a0d
0x0cc9b2…7777
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:
0x541997e9…30f5a0
1 conflict on slot
0x1ee00353e1…a9b4fe
Audit this contract →
← previous block
·
next block →
recent activity