pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,575,357
← previous block
next block →
recent activity
Analyzing
Block #84,575,357
10 transactions · 9 stateful · 2026-06-30 00:48:42 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,575,357
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
redeemDelegations
#4
executeBatch
#5
updatePosition
#6
0x0f6795d9
#7
0xed82b078
· blocks 1
#9
0x6a4312e2
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x29686688…0598
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0778f130…d05d
0x754704…b603
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
2 touches
0 conflicts
0x5149ba0e…d954
0x754704…b603
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xb3572c958a…0d9c4a
Audit this contract →
← previous block
·
next block →
recent activity