pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,239,805
← previous block
next block →
recent activity
Analyzing
Block #76,239,805
13 transactions · 10 stateful · 2026-05-22 10:07:37 UTC
Parallelism
77
/100
Blocked
30
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,239,805
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
batchUpdate
· blocks 1
#5
batchUpdate
· blocks 1
#8
redeemDelegations
· blocks 1
#10
updateDataFeedsValuesPartial
#11
deposit
#12
setData
#6
0xed82b078
· blocks 1
#9
redeemDelegations
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xbb9f2a…26f0
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x03226734…d6d2
0xa6afd3…d132
4 touches
1 conflict
0xf282c2b3…28b4
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0xab3526…fa38
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:
0xbb9f2a41…c726f0
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity