pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,537,086
← previous block
next block →
recent activity
Analyzing
Block #82,537,086
22 transactions · 19 stateful · 2026-06-20 14:02:13 UTC
Parallelism
73
/100
Blocked
42
%
Avg conflicts / tx
0.77
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,537,086
· 22 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0xab083028
· blocks 2
#2
batchCancelOrders
#6
batchUpdate
#7
batchUpdate
· blocks 1
#9
0xed82b078
· blocks 1
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#15
updateDataFeedsValuesPartial
#16
execFwdPositionOps
#17
execFwdPositionOps
#18
0x6a369ddd
#19
setData
#20
execOrders
· blocks 1
#3
0xed82b078
· blocks 5
#11
0xed82b078
· blocks 1
#21
execOrders
#4
0xed82b078
#5
batchUpdate
· blocks 3
#8
batchUpdate
· blocks 2
#10
0xed82b078
· blocks 1
#12
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w2
7
w0
8
w3
9
w0
10
w4
11
w1
12
w5
20
w0
21
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x905dbe77…bf05
0xa6afd3…d132
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity