pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,968,749
← previous block
next block →
recent activity
Analyzing
Block #82,968,749
25 transactions · 22 stateful · 2026-06-22 14:08:18 UTC
Parallelism
84
/100
Blocked
36
%
Avg conflicts / tx
0.64
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,968,749
· 25 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
0xed82b078
· blocks 2
#3
0xab083028
· blocks 3
#7
0x5a5d9a99
#8
0x5a5d9a99
· blocks 1
#12
updateDataFeedsValuesPartial
#13
aggregate3
#14
execFwdPositionOps
· blocks 1
#15
execFwdPositionOps
#16
updateDataFeedsValuesPartial
#18
execFwdPositionOps
#19
execute
#20
setData
#21
execOrders
· blocks 1
#23
execOrders
#24
0xc7e3ec2c
#4
0xab083028
· blocks 4
#9
0x5a5d9a99
#17
execFwdPositionOps
#22
execOrders
#5
0xab083028
· blocks 1
#10
0xed82b078
· blocks 1
#6
0x6ad2e98b
#11
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w0
4
w1
5
w2
6
w3
8
w0
9
w1
10
w2
11
w3
14
w0
17
w1
21
w0
22
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08913286…f0df
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
6 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity