pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,282,276
← previous block
next block →
recent activity
Analyzing
Block #106,282,276
38 transactions · 30 stateful · 2026-09-19 21:17:44 UTC
Parallelism
84
/100
Blocked
57
%
Avg conflicts / tx
0.82
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,282,276
· 38 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0xaf5e395a
· blocks 4
#3
0x0756e95c
#5
main_all
#6
main_all
#7
matchOrders
#8
0x6aaefbfb
#9
updatePrices
· blocks 3
#11
updatePrices
#16
0x5acec890
#17
0x5acec890
· blocks 1
#18
0x5acec890
#20
0x59558d29
#21
execPerpOps
#22
execPerpOps
#24
updateDataFeedsValuesPartial
#25
transferWithAuthorization
#26
setData
#27
0x62be7533
#30
forward
#34
0x6aaefbfb
#2
0xab083028
· blocks 5
#10
updatePrices
· blocks 2
#19
0x5acec890
· blocks 2
#4
0xf78cb219
· blocks 2
#12
updatePrices
· blocks 1
#15
0x4297b034
· blocks 1
#29
execFwdPositionOpsV2
· blocks 2
#13
updatePrices
#14
0xab083028
· blocks 3
#31
0xed82b078
· blocks 1
#33
execFwdPositionOpsV2
#35
execOrders
· blocks 2
#23
0xe3a3c9cc
#28
0x3f5c179b
· blocks 1
#36
execOrders
· blocks 1
#32
0xed82b078
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
9
w0
10
w1
12
w2
13
w3
14
w3
15
w2
17
w0
19
w1
23
w4
28
w4
29
w2
31
w3
32
w5
35
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd4e2f1c7…da8b
0x065c9d…c394
5 touches
3 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
10 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity