pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,313,704
← previous block
next block →
recent activity
Analyzing
Block #86,313,704
24 transactions · 22 stateful · 2026-07-08 01:58:55 UTC
Parallelism
71
/100
Blocked
45
%
Avg conflicts / tx
0.79
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,313,704
· 24 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
execute
#2
0x50a0b275
· blocks 1
#4
0x0c7abd22
· blocks 2
#9
execOrders
· blocks 1
#11
updateDataFeedsValuesPartial
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
0x62be7533
#15
execFwdPositionOps
#18
forward
#21
0x6a4daf56
#22
setData
#23
0xc7e3ec2c
#3
0x1094dc9f
· blocks 5
#5
0x0c7abd22
· blocks 1
#10
execOrders
#6
0xab083028
· blocks 2
#7
0xab083028
· blocks 2
#8
0xab083028
· blocks 3
#16
0x3f5c179b
#17
0x0c7abd22
· blocks 2
#19
0xed82b078
#20
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
6
w2
7
w3
8
w4
9
w0
10
w1
16
w4
17
w5
19
w6
20
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x6032eb71…e5b6
0xd32edf…ff58
5 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
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