pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,629,703
← previous block
next block →
recent activity
Analyzing
Block #81,629,703
13 transactions · 10 stateful · 2026-06-16 09:10:21 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,629,703
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
undelegate
#2
0xed82b078
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x1a945f9c
· blocks 1
#7
0x785f5745
#9
0x0c7abd22
#10
0xed82b078
#11
0xed82b078
#12
setData
#8
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0001
0x000000…1000
2 touches
0 conflicts
0x0b000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0006
0x000000…1000
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:
LeverUp: LeverUp
1 conflict on slot
0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block
·
next block →
recent activity