pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,626,947
← previous block
next block →
recent activity
Analyzing
Block #81,626,947
10 transactions · 10 stateful · 2026-06-16 08:52:00 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,626,947
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x39435dac
· blocks 1
#6
0x0c7abd22
#7
setData
#8
redeemDelegations
#9
0x39435dac
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5581d709…ab77
0x2a68ba…90c5
2 touches
0 conflicts
0x05ed88c1…9676
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x1017e868…fcc2
0x34b655…2a6f
2 touches
0 conflicts
0x1ec6f594…d4b3
0x34b655…2a6f
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
0xf6476f21e7…f83580
Audit this contract →
← previous block
·
next block →
recent activity