pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,262,662
← previous block
next block →
recent activity
Analyzing
Block #76,262,662
11 transactions · 9 stateful · 2026-05-22 12:39:38 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,262,662
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
redeemDelegations
· blocks 1
#3
reverseMessage
#4
updateDataFeedsValuesPartial
#5
setData
#6
updatePosition
#7
play
#8
0x39435dac
#10
0xf2eaccd1
#9
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x2825c7…5f33
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x04d0aa0a…eb73
0x6657d1…8ccc
2 touches
0 conflicts
0x0f6d2b23…f50c
0x6657d1…8ccc
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:
0x2825c759…235f33
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity