pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,654,926
← previous block
next block →
recent activity
Analyzing
Block #82,654,926
15 transactions · 10 stateful · 2026-06-21 03:11:35 UTC
Parallelism
87
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,654,926
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
removeLiquidityNATIVE
#3
0xa09e9040
· blocks 1
#5
execute
#6
execute
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x45761772
#10
forward
#11
forward
#12
0x0f6795d9
#13
0x0f6795d9
#14
setData
#4
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x963cfd49…150d
0x065c9d…c394
3 touches
1 conflict
0xf78e94ea…6101
0x065c9d…c394
3 touches
1 conflict
0xec00464c…fedb
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…000d
0x46a15b…4364
2 touches
0 conflicts
0x405787fa…0232
0x46a15b…4364
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
0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block
·
next block →
recent activity