pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,140,585
← previous block
next block →
recent activity
Analyzing
Block #76,140,585
13 transactions · 10 stateful · 2026-05-21 23:06:39 UTC
Parallelism
85
/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,140,585
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbb5d006a
#2
setPrice
#3
setPrice
#4
setPrice
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updatePrices
#8
updatePrices
#9
0x98717539
· blocks 1
#11
0xdbe723…999d
#12
setData
#10
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
2 touches
0 conflicts
0x81d67c49…e69c
0x3c2269…cf62
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
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity