pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,462,403
← previous block
next block →
recent activity
Analyzing
Block #76,462,403
13 transactions · 11 stateful · 2026-05-23 10:49:29 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,462,403
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
0x5339c59f
#3
0x5bf9264c
· blocks 1
#5
0x1a945f9c
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
updatePriceFeedsIfNecessary
#11
0x0f6795d9
#12
0x0f6795d9
#4
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xc9cea23c…29e5
0x1efe02…37d6
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x4060605b…75a3
0x3bd359…433a
2 touches
0 conflicts
0x57a37dda…8712
0x3bd359…433a
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
0xea02471df2…601539
Audit this contract →
← previous block
·
next block →
recent activity