pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,465,469
← previous block
next block →
recent activity
Analyzing
Block #76,465,469
10 transactions · 8 stateful · 2026-05-23 11:09:56 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,465,469
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
updateDataFeedsValuesPartial
#3
0x5ff249…d908
#4
0x98717539
· blocks 1
#5
redeemDelegations
#6
setData
#7
0x42bbae7a
#9
0x0f6795d9
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xac5a9a7e…693e
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0544396e…9f61
0x34b655…2a6f
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
2 touches
0 conflicts
0x2317b40a…947d
0x34b655…2a6f
2 touches
0 conflicts
0x3a150206…3305
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity