pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,016,412
← previous block
next block →
recent activity
Analyzing
Block #81,016,412
10 transactions · 10 stateful · 2026-06-13 13:05:26 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,016,412
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
0x23afbff3
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
0x0c7abd22
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x064a3cb8…c43e
0x09475a…400f
2 touches
0 conflicts
0xd420023a…cf6a
0x09475a…400f
2 touches
0 conflicts
0x34e65d5c…838e
0xd5d960…eaee
2 touches
0 conflicts
0x541a74a9…d0c2
0xd5d960…eaee
2 touches
0 conflicts
0x88ef4191…6de8
0xd5d960…eaee
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
0xffc2f21efe…ecb393
Audit this contract →
← previous block
·
next block →
recent activity