pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,244,432
← previous block
next block →
recent activity
Analyzing
Block #76,244,432
13 transactions · 8 stateful · 2026-05-22 10:38:26 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,244,432
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x5bf9264c
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
0x0f6795d9
· blocks 1
#9
0x0f6795d9
#10
0x0f6795d9
#11
setData
#12
handleOps
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x3013c848…bd3c
0x34b655…2a6f
4 touches
1 conflict
0x1be8019f…b769
0x34b655…2a6f
2 touches
0 conflicts
0x48e4e1cf…f91b
0x34b655…2a6f
2 touches
0 conflicts
0x4c344860…c0d0
0x34b655…2a6f
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
0x5b6af0070f…160f35
Audit this contract →
← previous block
·
next block →
recent activity